home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950726-19950929
/
000330_news@columbia.edu_Sat Sep 9 11:13:25 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA21269
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Sat, 9 Sep 1995 20:42:45 -0400
Received: by apakabar.cc.columbia.edu id AA13781
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Sat, 9 Sep 1995 20:42:44 -0400
Path: news.columbia.edu!sol.ctr.columbia.edu!howland.reston.ans.net!swrinde!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MS-DOS Kermit 3.14 Second Edition
Message-Id: <1995Sep9.171325.60974@cc.usu.edu>
Date: 9 Sep 95 17:13:25 MDT
References: <3tf3n7$2tl@apakabar.cc.columbia.edu> <2989@sun3.IPSWITCH.COM>
Organization: Utah State University
Lines: 48
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <2989@sun3.IPSWITCH.COM>, ddl@harvard.edu (Dan Lanciani) writes:
> In article <1995Sep9.114915.60947@cc.usu.edu>, jrd@cc.usu.edu (Joe Doupnik) writes:
>
> [...]
> | Ugh(tm). Arcnet with ODI has its share of problems when it comes
> | to ARP.
>
> ODI makes your application completely media-independent... :) As long
> as your medium looks like Ethernet/802.3/802.5... :(
Right, sure. I understand ODI rather well, but the picky hardware
dependent things, say the other guy's MAC address, requires special
handling outside the otherwise CS-clean ODI material. ARP is the dirtiest
of the hardware parts.
> |An ARCnet MAC address is one byte long, yet ODI provides six byte
> | MAC addresses. Which end of that string will the byte appear? Undocumented.
>
> I seem to recall that the answer here is that there isn't a simple answer.
> There is certainly an end where the node id appears (check the ODIPKT sources;
> I forget which end it is), but there are other cases where all six bytes are
> significant. For example, I think you get into trouble unless you set all
> six bytes to ff for a broadcast, at least on some drivers.
You are beginning to see what the muddle is.
> | The medium ident appearing in an ARP packet reflects the kind of wiring,
> | 6 for Ethernet and presumably 7 for ARCnet. I did make some changes in the
> | MAC address extraction procedure in MSK mark II, and maybe something got
> | broken.
>
> The poster with the ARCNet problem might want to try running over ODIPKT.
> It understands all these details and presents a fake Ethernet driver
> interface to the client (kermit in this case). I did all the original
> development with [T]RXNET so it should work with that if anything. :)
Good suggestion Dan. Tnx.
> | I tested earlier MSK's with ARCnet, and honestly I found that
> | arrangment to be flakey at best. It's not MSK but rather whatever IP
> | routing a NW server does in that case.
>
> Funny, I've found most users of the server's IP routing features to have
> no trouble. It does (did?) enforce some subnetting restrictions a little
> too enthusiastically, but I guess one can't blame them for following
> the RFCs...
It's not straight IP routing that's the problem; it's the media
conversion involved (all that grubby hardware-specific stuff on the ARCnet
side).
Thanks for the comments,
Joe D.